-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial tests for writing functions #31
Conversation
Notes: HEATOM is not supported in mosdef-GOMC writers, it always writes ATOM in pdb files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ATOM is currently the only output for mosdef-GOMC pdb files.
Should we put all these test files in the utils/files (https://github.com/GOMC-WSU/MoSDeF-dihedral-fit/tree/main/mosdef_dihedral_fit/utils/files), where all the other ones are? Maybe I don’t understand the reason. |
In terms of packaging, typically you want files that are solely there for test validation to exist in the /tests module. /utils/files would be something more like file templates or something that is actually used during the course of operating the package. |
Looks like macos and ubuntu tests are giving different outputs for the fifth element of the dihedral angle (macos=+180.0, ubuntu=-180.0). Probably something with the get_matching_dihedral_info_and_opls_fitting_data Looks like maybe a bug in this line:
Should be?
Regardless, I'm guessing the difference is coming from a dot or cross product direction. |
Yeah, I agree, you are likely correct here |
That is fine, I think we can support HETATM since that's what you get from MoSDeF pdb writers and as far as I can tell the data can get parsed the same way. |
for more information, see https://pre-commit.ci
9517dbd
to
b2d219b
Compare
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Since we created the same files again in "test/files" (used for unit tests). Let's remove all the files from "utils/files/" and move them to "test/files", in a quick next PR. This way all the test files are in 1 location.....
This PR aims to add tests for all of the utility readers and writers used in the repo. To aid in this testing, a set of files are all stored in
tests/files/
for ease of access and testing on.